Four-dimensional imaging system for cardiovascular dynamics

ABSTRACT

A system may receive imaging data generated by an imaging device directed at a heart. The system may receive a first input operation indicative of a selected time-frame. The system may display images of the heart based on the intensity values mapped to the selected time-frame. The system may receive, based on interaction with the images, an apex coordinate and a base coordinate. The system may calculate, based on the apex coordinate and the base coordinate, a truncated ellipsoid representative an endocardial or epicardial boundary of the heart. The system may generate a four-dimensional mesh comprising three-dimensional vertices spaced along the mesh. The system may overlay, on the displayed images, markers representative of the vertices. The system may receive a second input operation corresponding to a selected marker. The system may enhance the mesh by adjusting or interpolating vertices across multiple time-frames.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation application of U.S. patentapplication Ser. No. 16/903,039, filed Jun. 16, 2020, and is related toand claims the benefit of U.S. Provisional Application No. 62/971,465filed Feb. 7, 2020, each of which is hereby incorporated by reference inits entirety.

TECHNICAL FIELD

This disclosure relates to medical imaging and, in particular, tocardiovascular medical imaging.

BACKGROUND

Congestive heart failure is a common sequela of myocardial infarction(Ml), cardiac hypertrophy, and other pathologies associated with adverseremodeling. Despite clear diagnostic criteria of late-stage heartfailure, the mechanical factors that drive cardiac early-stageremodeling remains unclear. The majority of ultrasound studies, however,still rely on 2D approaches to quantify global reductions of leftventricular (LV) function.

BRIEF DESCRIPTION OF THE DRAWINGS

The patent or application file contains at least one drawing executed incolor. Copies of this patent or patent application with colordrawings(s) will be provided by the Office upon request and payment ofthe necessary fee.

The embodiments may be better understood with reference to the followingdrawings and description. The components in the figures are notnecessarily to scale. Moreover, in the figures, like-referenced numeralsdesignate corresponding parts throughout the different views.

FIG. 1 illustrates a first example of a system 100 for imaging organdynamics;

FIG. 2 illustrates a flow diagram of left ventricle imaging providing bythe system;

FIG. 3 illustrates a first example of a graphical user interface

FIG. 4 illustrates a second example of a graphical user interface forpre-processing imaging data;

FIG. 5 illustrates a third example of a graphical user interface withrotated imaging data;

FIG. 6 illustrates a fourth example of a graphical user interface withan identified base location;

FIG. 7 illustrates a fifth example of a graphical user interface with anidentified apex location;

FIG. 8 illustrates a sixth example of a graphical user interface with asuper-imposed boundary at a first time-frame;

FIG. 9 illustrates a seventh example of a graphical user interface witha super-imposed boundary at a second time-frame;

FIG. 10 illustrates an eighth example of a graphical user interface witha movable marker;

FIG. 11 illustrates a ninth example of a graphical user interface with asuper-imposed boundary after contouring;

FIG. 12 illustrates a tenth example of a graphical user interface withan example plot of ventricular volume throughout a representativecardiac cycle;

FIG. 13 illustrates an example of a spatiotemporal map ofcircumferential strain across the cardiac cycle based on the endocardialborder kinematics; and

FIG. 14 illustrates a second example of the system 100.

DETAILED DESCRIPTION

System and methods for four-dimensional imaging for organ dynamics areprovided. By way of introductory example, the system may receive imagingdata generated by an imaging device directed at a heart. The imagingdata may include intensity values in three spatial dimensions andtime-frame identifiers associated with the intensity values. Thetime-frame identifiers may identify frames sampled over a time window ofa cardiac cycle. The system may receive a first input operationindicative of a selected time-frame. The system may display images ofthe heart, or a portion thereof, based on the intensity values mapped tothe selected time-frame. The system may receive, based on interactionwith the images, an apex coordinate and a base coordinate for theselected time-frame, the apex coordinate representative of the apex ofthe left-ventricle and the base coordinate representative of the base ofthe left-ventricle. The system may calculate, based on the apexcoordinate and the base coordinate, a truncated ellipsoid representativean endocardial or epicardial boundary of the heart. The system maygenerate a four-dimensional mesh comprising a plurality ofthree-dimensional vertices mapped to a time-frame value correspondingselected time-frame, the three-dimensional vertices spaced along thetruncated ellipsoid. The system may overlay, on the displayed images, aplurality of adjustable markers representative of the vertices that aremapped with the selected time-frame. The system may receive a secondinput operation corresponding to a selected marker. The system mayenhance the mesh by adjusting or interpolating vertices across multipletime-frames.

A technical advancement provided in the system and methods describedherein is a framework for quantifying regional kinematics across theentire left-ventricle, which incorporates motion of the left-ventricularbase and apex throughout the cardiac cycle in output boundary meshes.This approach corrects for through-plane motion inherent to planarimaging of tissue with substantial gross movement, such as theleft-ventricle of the heart. Although conventional short-axismotion-mode (SAXMM) ultrasound and cine magnetic resonance imaging (MRI)are two of the most prevalent strategies used for quantifying cardiacfunction, there are few notable limitations including imprecision,inaccuracy, and geometric assumptions with ultrasound, or large andcostly systems with substantial infrastructure requirements with MRI.4-dimensional ultrasound provides comparable information to cine MRIthrough spatiotemporally synced imaging of cardiac motion, whilereducing user variability associated with traditional ultrasoundapproaches.

Another example of a technical advancement provided by the system andmethods described herein is the ability to integrate 4-dimensionalultrasound with three-dimensional strain mapping to longitudinallycharacterize LV mechanics. The ability to quantify regional strain isparticularly useful when assessing remodeling due to myocardialinfarction or pathological hypertrophy. Additional or alternativetechnical advancements are made evident by the system and methodsdescribed herein.

FIG. 1 illustrates a first example of a system 100. The system mayinclude an imaging device 102 suited for diagnostic imaging. The imagingdevice 102 may include, for example, a device that generates imagerywith ultrasound, magnetic resonance imaging, and/or computed tomography.The imaging device 102 may generate imaging data. The imaging data mayinclude a matrix of intensity values where each intensity value ismapped to a physical location in space (x, y, z). In some examples, theimaging data may be four-dimensional with three spacial dimensions and atemporal dimension (t).

The system 100 may include an organ modeling framework 104 to modelorgans that move dynamically with cardiorespiratory rhythms. Asdescribed in various examples herein, the organ may include the heart,or a portion of the heart such as the left ventricle. By way ofnon-limiting example, the organ or portions of organ may include thethoracic aorta, abdominal aorta, abdominal organs, carotid arteries,etc. The modeling framework 104 may receive imaging data and generate amodel of the organ. The model may include a mesh of points defining themorphology of the organ at multiple points across the time-domain.

The modeling framework 104 may communicate with a terminal 106 togenerate a graphical user interface 108. A user may interact with theuser interface 108 to provide various inputs for modeling the organ. Themodeling framework 104 may provide various controls to enable generationand enhancement of a model (or models).

In some examples, the model may represent the epicardial and/orendocardial barriers of the of a left ventricle of a heart.

FIG. 2 illustrates a flow diagram of left ventricle imaging providing bythe system 100. Reference to FIG. 1 and FIG. 2 are made throughout theremaining description.

The modeling framework 104 may receive imaging data (202). For example,the imaging data may be received in real-time from the imaging device102. Alternatively, the imaging data may be previously generated andaccessed from stored memory or a network location.

In some examples, the imaging device 102 may send intensity valuesrepresentative of pixels, which are pre-processed and stored in a 4Ddata structure with three special dimensions and one temporal dimension.

The modeling framework 104 may receive a selected time-frame (203). Themodeling framework 104 may cause images of a heart to be displayed(204). For example, the images of the heart that are displayed may begenerated based on imaging data associated with the selected time-frame.

FIG. 3 illustrates an example of the graphical user interface 108.Images 302-306 are displayed by separating imaging data into orthogonalplanes. The graphical user interface may include a first image 302rendered to view a first cross section of the imaging data (x-y plane).A second image 304 rendered to view a second cross section of theimaging data orthogonal to the first cross section (x-z plane). A thirdimage 306 may be rendered to view a third cross section orthogonal tothe first and second cross section (x-z plane).

The user interface may have a time-frame selection control 308. Thetime-frame selection control may detect or respond to user input. Inresponse to interaction with the time-frame selection control 308, themodeling framework 104 may receive a time-frame selection. Thetime-frame selection may identify one or more time-frames sampled fromthe imaging data.

Relative spacing between pixels is determined using the physicaldimensions of each axis inputted. All three views may be synchronized toshow the same relative time-frame.

FIG. 4-8 illustrates various examples of the graphical user interface108 involved in pre-processing the imaging data for modeling. Themodeling system may provide the user interfaces to assist with thepre-processing.

After receiving the imaging data, the imaging data may be digitallyresampled to an isotropic voxel resolution (i.e. all voxels have equaldimensions). In various examples, the modeling framework 104 may receivea rotate command corresponding to an isolated axis. The rotate commandmay correspond to an input operation with controls 402 respectivelyassociated with the isolated axis. In response to the rotate command,the modeling framework may rotate spatial locations by which intensityvalues of the inputted data is sampled to align the base and apex of theleft ventricle along the z-axis. Then, the modeling framework 104 maytransform the four-dimensional data corresponding to the image based onthe rotations. Accordingly, the imaging may be rotated to standardizealignment. For example, to ensure the z-axis goes through the apex ofthe heart and approximate center of the base of the heart, the imagedata may be re-oriented to coordinate axes oblique to the input axes.The cross-sectional locations (z-axis) of the base and apex of the heartare tracked through time (t-axis).

Referring to FIG. 4, data may be reoriented around a marker (such as acrosshair or the like). The graphical user interface 108 may provide oneor more controls to change the location of the crosshairs in theimage(s). In some examples, the graphical user interface 108 may respondto touch operations (i.e. on the display of the terminal) detected bythe terminal 106 and/or modeling framework 104. The crosshairs and/ordisplayed images may move in response to the detected operations.

Referring to FIG. 4, a user may cause rotation via an input operationand/or by specifying axis-specific degrees of rotation. The modelingframework 104 may calculate the appropriate transformation matrix(either due to translation or rotation) to apply to the imaging datasample point locations, and then finally draws from that transformed(i.e. re-oriented) grid of physical locations to sample a new or updatedimaging dataset using trilinear interpolation, as shown in FIG. 5.

To form an initial model, the modeling framework 104 may receive initialinput data, which is used to approximate the endocardial and epicardialboundaries of a heart or a portion thereof. For example, in the case ofa left ventricle, the input data may include an apex coordinate and abase coordinate (206). The apex coordinate may identify a specifiedlocation of the apex of a left ventricle and the base may identify aspecified location of the base of the left ventricle.

In some examples, the apex coordinates may be specified by selecting aninput mode. For example, the user interface may include a boundaryselection control (404). The boundary selection control 404 may bemodified to select “base” or “apex”.

As illustrated in FIG. 6-7, respective border positions (base/apex) aretracked by having the user define known locations throughout arepresentative cardiac cycle (black dots shown in FIGS. 6-7). Theframework will interpolate the remaining positions, ensuring the curvereturns to its initial position. By tracking these boundaries, theframework accounts for through-plane motion often not accounted for inother analysis strategies.

The modeling framework 104 may calculate a truncated ellipsoidrepresentative an endocardial or epicardial boundary of the heart (208).Referring to FIGS. 8-9, a truncated ellipsoid is created at each timepoint across a representative cardiac cycle. The ellipsoid is createdwith its center along the z-axis at 70% of the distance from the cardiacapex to the base. Similar to tracking the base and apex, the ratiobetween the width and length of the ellipsoid may then be modified toaccount for circumferential wall movement throughout the cardiac cycle.From the final set of time-dependent ellipsoid volumes, initialestimations of global cardiac metrics are calculated (i.e. ejectionfraction, stroke volume, etc.). As seen in the last two images, imagehistogram equalization can be applied to increase local contrast and aidthe user in defining landmarks.

FIG. 8 illustrates the truncated ellipsoid overlay for a singletime-frame. Cross-section markers 802A-C of a first truncated ellipsoid,representative of the epicardial boundary, may be super-imposed on theimage for a specified time-frame. Similarly, cross-section markers804A-C of a second truncated ellipsoid, representative of theendocardial boundary, may be superimposed on the images for a specifiedtime-frame.

The positioning of the truncated ellipsoids may be determined based onthe aforementioned base and apex locations, and ratio of ellipsoid widthto length, using the following equations and an array of samples alongthe z-axis:

$\begin{matrix}{{radii} = {\left( {{length} \cdot {ratio}_{{radius}/{length}}} \right)\sqrt{1 - \left( \frac{z}{length} \right)^{2}}}} & \left( {{eq}.\mspace{14mu} 1} \right) \\{{length} = {\left( {z_{base} - z_{apex}} \right) \cdot 0.7}} & \left( {{eq}.\mspace{14mu} 2} \right)\end{matrix}$

As illustrated in FIG. 9, positioning of truncated ellipsoids may berecalculated and repositioned at specific time-frames using thegraphical user interface. For example, cross-section markers 902A-C of arepositioned truncated ellipsoid representative of the epicardialboundary may be super-imposed on the image for a secondary time-frame.Similarly, cross-section markers 904A-C of a repositioned truncatedellipsoid representative of the endocardial boundary may be superimposedon the images for the corresponding secondary time-frame.

The modeling framework 104 may generate a mesh comprising a plurality ofvertices along the ellipsoid (210). In some examples, the mesh mayinclude a four-dimensional mesh where the vertices include sampledpoints along the ellipsoids at various times.

The myocardium dynamics framework and/or the graphical user interfaceplatform may overlay a plurality of moveable markers representative of asubset of vertices intended to track the tissue borders (212).

FIGS. 10-11 illustrate an example of the graphical user interface 108for contouring 4D mesh data. The mesh may initial include equally spacedpoints around (short-axis view) and down (long-axis view) the z-axis.The mesh may be enhanced through adjustment, interpolation, and/or othermeasurements derived from interaction with the graphical user interface(204).

For example, a vertex of the mesh may be displayed using a marker 1002.The marker may be selected and/or movable to adjust the contours of themesh at a specified time. The marker 1002 may become highlighted (i.e.embolden or changed color) to specify selection. In response to movementof the marker 1002, the shape (i.e. visible lines) of the crosssection(s) 802(A-B) may change in one or more of the images.Accordingly, the controls of the left ventricle may be tracked andadjusted across the cardiac cycle by adjustment of the markers, as shownin FIG. 11. The tracked makers may include 24 points per boundary (i.e.6 rotations around [30,90,150,210,270,330 deg] the z-axis and 4 parallelslices equally spaced from the apex to base). Similar to tracking thebase and apex locations, the user 1) selects an individual point basedon rotation and slice, 2) defines known locations of that point (blackdots) throughout the cardiac cycle (i.e. distances from the z-axis(yellow line)), and 3) the computer interpolates a curve of positionsfor that point.

The images on which boundaries are tracked are sliced from the orienteddata, using the previously defined slice locations. For example, the setof short-axis slices corresponding to the base will follow the z-axislocations of the base defined in the prior tab. This ensures thatpotential errors due to through-plane motion are minimized duringboundary mesh calculations.

In some examples, the endocardial or epicardial boundary may beinterpolated. For example, additional points for corresponding times maybe created by fitting hobby-splines through the 24-point sub-grid thatwas modified in the “Contouring” tab. Then from those hobby-splines, anequally spaced grid of points across the boundary (e.g. 60×60; around xdown) is calculated.

The modeling framework 104 may display, or cause display of, theenhanced mesh. FIGS. 12-13 illustrate an example of the graphical userinterface 108 displaying a first enhanced mesh for an endocardialboundary and a second enhanced mesh for an epicardial boundary.

FIG. 12 illustrates an example plot of ventricular volume throughout arepresentative cardiac cycle. Changes in physical location (x,y,z) ofeach point in that standardized grid provide the basis for calculatingmetrics of heart kinematics. For example, the user interface 108 in FIG.12 illustrates circumferential strain represented by the percent changein endocardial boundary perimeter for every z-position down the 4D gridacross the cardiac cycle. Three-dimensional renderings on the right-sideof the GUI are created using Delaunay Triangulation between adjacentpoints and every triangular face can be colored according to thequantitative value that position represents.

In some examples, the modeling framework 104 may quantify variousmetrics of kinematics within the left ventricle across the cardiaccycle. For example, the modeling framework 104 may calculate, based onthe endocardial and epicardial meshes, a regional metric of boundarykinematics and/or a global metric of cardiac function. The regionalmetric of boundary kinematics may include, for example, circumferentialstrain, longitudinal strain, radial strain, degrees of rotation, theprincipal component of Green-Lagrange strain, or a combination thereof.The global metric of cardiac function may include, for example, ejectionfraction, cardiac output, stroke volume, left ventricular mass, or acombination thereof.

FIG. 13 illustrates an example of a spatiotemporal map ofcircumferential strain across the cardiac cycle based on the endocardialand epicardial boundaries. The modeling framework 104 may measuredisplacement of vertices between different time-frames over a playbackperiod. The modeling framework 104 may determine color values based onthe calculated value of circumferential strain at that location in spaceand time. For example, a color value may be associated with a range anda color value may be selected in response to the measured change beingwithin the range. The modeling framework 104 may generate an animationto illustrate circumferential strain representative by the color valuesover the playback period.

FIG. 14 illustrates a second example of the system 100. The system 100may include communication interfaces 812, input interfaces 828 and/orsystem circuitry 814. The system circuitry 814 may include a processor816 or multiple processors. Alternatively or in addition, the systemcircuitry 814 may include memory 820.

The processor 816 may be in communication with the memory 820. In someexamples, the processor 816 may also be in communication with additionalelements, such as the communication interfaces 812, the input interfaces828, and/or the user interface 818. Examples of the processor 816 mayinclude a general processor, a central processing unit, logicalCPUs/arrays, a microcontroller, a server, an application specificintegrated circuit (ASIC), a digital signal processor, a fieldprogrammable gate array (FPGA), and/or a digital circuit, analogcircuit, or some combination thereof.

The processor 816 may be one or more devices operable to execute logic.The logic may include computer executable instructions or computer codestored in the memory 820 or in other memory that when executed by theprocessor 816, cause the processor 816 to perform the operations theleft ventricle modeling framework 104 and/or the system 100. Thecomputer code may include instructions executable with the processor816.

The memory 820 may be any device for storing and retrieving data or anycombination thereof. The memory 820 may include non-volatile and/orvolatile memory, such as a random access memory (RAM), a read-onlymemory (ROM), an erasable programmable read-only memory (EPROM), orflash memory. Alternatively or in addition, the memory 820 may includean optical, magnetic (hard-drive), solid-state drive or any other formof data storage device. The memory 820 may include at least one of themodeling framework 104 and/or the system 100. Alternatively or inaddition, the memory may include any other component or sub-component ofthe system 100 described herein.

The user interface 818 may include any interface for displayinggraphical information. The system circuitry 814 and/or thecommunications interface(s) 812 may communicate signals or commands tothe user interface 818 that cause the user interface to displaygraphical information. Alternatively or in addition, the user interface818 may be remote to the system 100 and the system circuitry 814 and/orcommunication interface(s) may communicate instructions, such as HTML,to the user interface to cause the user interface to display, compile,and/or render information content. In some examples, the contentdisplayed by the user interface 818 may be interactive or responsive touser input. For example, the user interface 818 may communicate signals,messages, and/or information back to the communications interface 812 orsystem circuitry 814.

The system 100 may be implemented in many ways. In some examples, thesystem 100 may be implemented with one or more logical components. Forexample, the logical components of the system 100 may be hardware or acombination of hardware and software. The logical components may includethe modeling framework 104 or any component or subcomponent of thesystem 100. In some examples, each logic component may include anapplication specific integrated circuit (ASIC), a Field ProgrammableGate Array (FPGA), a digital logic circuit, an analog circuit, acombination of discrete circuits, gates, or any other type of hardwareor combination thereof. Alternatively or in addition, each component mayinclude memory hardware, such as a portion of the memory 820, forexample, that comprises instructions executable with the processor 816or other processor to implement one or more of the features of thelogical components. When any one of the logical components includes theportion of the memory that comprises instructions executable with theprocessor 816, the component may or may not include the processor 816.In some examples, each logical component may just be the portion of thememory 820 or other physical memory that comprises instructionsexecutable with the processor 816, or other processor(s), to implementthe features of the corresponding component without the componentincluding any other hardware. Because each component includes at leastsome hardware even when the included hardware comprises software, eachcomponent may be interchangeably referred to as a hardware component.

Some features are shown stored in a computer readable storage medium(for example, as logic implemented as computer executable instructionsor as data structures in memory). All or part of the system and itslogic and data structures may be stored on, distributed across, or readfrom one or more types of computer readable storage media. Examples ofthe computer readable storage medium may include a hard disk, a floppydisk, a CD-ROM, a flash drive, a cache, volatile memory, non-volatilememory, RAM, flash memory, or any other type of computer readablestorage medium or storage media. The computer readable storage mediummay include any type of non-transitory computer readable medium, such asa CD-ROM, a volatile memory, a non-volatile memory, ROM, RAM, or anyother suitable storage device.

The processing capability of the system may be distributed amongmultiple entities, such as among multiple processors and memories,optionally including multiple distributed processing systems.Parameters, databases, and other data structures may be separatelystored and managed, may be incorporated into a single memory ordatabase, may be logically and physically organized in many differentways, and may implemented with different types of data structures suchas linked lists, hash tables, or implicit storage mechanisms. Logic,such as programs or circuitry, may be combined or split among multipleprograms, distributed across several memories and processors, and may beimplemented in a library, such as a shared library (for example, adynamic link library (DLL).

All of the discussion, regardless of the particular implementationdescribed, is illustrative in nature, rather than limiting. For example,although selected aspects, features, or components of theimplementations are depicted as being stored in memory(s), all or partof the system or systems may be stored on, distributed across, or readfrom other computer readable storage media, for example, secondarystorage devices such as hard disks, flash memory drives, floppy disks,and CD-ROMs. Moreover, the various logical units, circuitry and screendisplay functionality is but one example of such functionality and anyother configurations encompassing similar functionality are possible.

The respective logic, software or instructions for implementing theprocesses, methods and/or techniques discussed above may be provided oncomputer readable storage media. The functions, acts or tasksillustrated in the figures or described herein may be executed inresponse to one or more sets of logic or instructions stored in or oncomputer readable media. The functions, acts, or tasks are independentof the particular type of instructions set, storage media, processor orprocessing strategy and may be performed by software, hardware,integrated circuits, firmware, micro code and the like, operating aloneor in combination. Likewise, processing strategies may includemultiprocessing, multitasking, parallel processing, and the like. In oneexample, the instructions are stored on a removable media device forreading by local or remote systems. In other examples, the logic orinstructions are stored in a remote location for transfer through acomputer network or over telephone lines. In yet other examples, thelogic or instructions are stored within a given computer and/or centralprocessing unit (“CPU”).

Furthermore, although specific components are described above, methods,systems, and articles of manufacture described herein may includeadditional, fewer, or different components. For example, a processor maybe implemented as a microprocessor, microcontroller, applicationspecific integrated circuit (ASIC), discrete logic, or a combination ofother type of circuits or logic. Similarly, memories may be DRAM, SRAM,Flash or any other type of memory. Flags, data, databases, tables,entities, and other data structures may be separately stored andmanaged, may be incorporated into a single memory or database, may bedistributed, or may be logically and physically organized in manydifferent ways. The components may operate independently or be part of asame apparatus executing a same program or different programs. Thecomponents may be resident on separate hardware, such as separateremovable circuit boards, or share common hardware, such as a samememory and processor for implementing instructions from the memory.Programs may be parts of a single program, separate programs, ordistributed across several memories and processors.

A second action may be said to be “in response to” a first actionindependent of whether the second action results directly or indirectlyfrom the first action. The second action may occur at a substantiallylater time than the first action and still be in response to the firstaction. Similarly, the second action may be said to be in response tothe first action even if intervening actions take place between thefirst action and the second action, and even if one or more of theintervening actions directly cause the second action to be performed.For example, a second action may be in response to a first action if thefirst action sets a flag and a third action later initiates the secondaction whenever the flag is set.

To clarify the use of and to hereby provide notice to the public, thephrases “at least one of <A>, <B>, . . . and <N>” or “at least one of<A>, <B>, <N>, or combinations thereof” or “<A>, <B>, . . . and/or <N>”are defined by the Applicant in the broadest sense, superseding anyother implied definitions hereinbefore or hereinafter unless expresslyasserted by the Applicant to the contrary, to mean one or more elementsselected from the group comprising A, B, . . . and N. In other words,the phrases mean any combination of one or more of the elements A, B, .. . or N including any one element alone or the one element incombination with one or more of the other elements which may alsoinclude, in combination, additional elements not listed. While variousembodiments have been described, it will be apparent to those ofordinary skill in the art that many more embodiments and implementationsare possible. Accordingly, the embodiments described herein areexamples, not the only possible embodiments and implementations.

What is claimed is:
 1. A method, comprising: receiving imaging data of aheart, the imaging data comprising intensity values in three spatialdimensions; displaying an image of the heart, or a portion thereof,based on the imaging data; receiving, based on interaction with theimages, an apex coordinate and a base coordinate, the apex coordinaterepresentative of the apex of the heart and the base coordinaterepresentative of the base of the heart; calculating, based on the apexcoordinate and the base coordinate, a first truncated ellipsoidrepresentative an endocardial boundary of the heart and a secondtruncated ellipsoid representative of an epicardial boundary of theheart; generating a first mesh and a second mesh, the first meshcomprising a plurality of vertices along the first truncated ellipsoidand the second mesh comprising a plurality of vertices along the secondtruncated ellipsoid; and displaying a plurality of markersrepresentative of at least one of the vertices of the first truncatedellipsoid and the vertices of the second truncated ellipsoid.
 2. Themethod of claim 1, wherein the endocardial boundary of the heart is theendocardial boundary of a left ventricle of the heart and the epicardialboundary is the epicardial boundary of the left ventricle of the heart.3. The method of claim 1, wherein displaying the plurality of markersfurther comprises overlaying the plurality of markers on the displayedimage.
 4. The method of claim 3, wherein the markers are movablemarkers.
 5. The method of claim 1, further comprising: displaying athree-dimensional render of the heart based on the first and secondmeshes.
 6. The method of claim 5, wherein the first and second meshesare each a four dimensional comprising spatial data mapped to time-frameidentifiers, wherein displaying the three-dimensional render of theheart based on the mesh further comprises: generating an animation ofthe heart based on the changes in the spatial data over a plurality offrames in a time window.
 7. The method of claim 5, wherein displayingthe three-dimensional render of the heart based on the first and secondmeshes further comprises: measuring changes of location betweencorresponding vertices at different time-frames over a playback period;determining a plurality of color values based on the measured changes oflocation; and generating an animation to illustrate circumferentialstrain representative by the color values over the playback period. 8.The method of claim 1, further comprising: calculating, based on atleast one of the first or second meshes, regional metrics of boundarykinematics and global metrics of cardiac function, the regional metricsof boundary kinematics comprising circumferential strain, longitudinalstrain, radial strain, degrees of rotation, the principal component ofGreen-Lagrange strain, or a combination thereof, and the global metricsof cardiac function comprising ejection fraction, cardiac output, strokevolume, left ventricular mass, or a combination thereof; and displayingthe regional metrics of boundary kinematics and global metrics ofcardiac function.
 9. The method of claim 1, wherein displaying the imageof the heart based on the imaging data further comprises generating atleast two images representative of orthogonal cross-sections through theimaging data; and generating an axis marker on each respective image,indicative of a location where respective planes for the other two imagecross orthogonally.
 10. The method of claim 9, further comprisingreceiving a rotate command corresponding to an isolated axis; rotatingspatial locations by which intensity values of the inputted data issampled to align the base and apex of the left ventricle along the axis;and transforming the imaging data corresponding to the image based onthe rotations.
 11. A system, comprising: a processor, the processorconfigured to: receive imaging data of a heart, the imaging datacomprising intensity values in three spatial dimensions; cause an imageof the heart, or a portion thereof, to be displayed based on the imagingdata; receive, based on interaction with the image, an apex coordinateand a base coordinate, the apex coordinate representative of the apex ofthe heart and the base coordinate representative of the base of theheart; calculate, based on the apex coordinate and the base coordinate,a first truncated ellipsoid representative an endocardial boundary ofthe heart and a second truncated ellipsoid representative of anepicardial boundary of the heart; generate a first mesh and a secondmesh, the first mesh comprising a plurality of vertices along the firsttruncated ellipsoid and the second mesh comprising a plurality ofvertices along the second truncated ellipsoid; and cause display of aplurality of markers representative of at least one of the vertices ofthe first truncated ellipsoid and the vertices of the second truncatedellipsoid.
 12. The system of claim 11, wherein the endocardial boundaryof the heart is the endocardial boundary of a left ventricle of theheart and the epicardial boundary is the epicardial boundary of the leftventricle of the heart.
 13. The system of claim 11, wherein to causedisplay of the plurality of markers, the processor is further configuredto: cause display of the plurality of markers overlayed on the image ofthe heart.
 14. The system of claim 13, wherein the markers are movablemarkers.
 15. The system of claim 1, wherein the processor is furtherconfigured to: output a three-dimensional render of the heart based onthe first and second meshes.
 16. The system of claim 15, wherein thefirst and second meshes are each a four dimensional comprising spatialdata mapped to time-frame identifiers, wherein to output thethree-dimensional render of the heart based on the mesh, the processoris further configured to: generate an animation of the heart based onthe changes in the spatial data over a plurality of frames in a timewindow.
 17. The system of claim 15, wherein to output thethree-dimensional render of the heart based on the first and secondmeshes, the processor is further configured to: measure changes oflocation between corresponding vertices at different time-frames over aplayback period; determine a plurality of color values based on themeasured changes of location; and generate an animation to illustratecircumferential strain representative by the color values over theplayback period.
 18. The system of claim 11, wherein the processor isfurther configured to: calculate, based on at least one of the first orsecond meshes, regional metrics of boundary kinematics and globalmetrics of cardiac function, the regional metrics of boundary kinematicscomprising circumferential strain, longitudinal strain, radial strain,degrees of rotation, the principal component of Green-Lagrange strain,or a combination thereof, and the global metrics of cardiac functioncomprising ejection fraction, cardiac output, stroke volume, leftventricular mass, or a combination thereof; and output the regionalmetrics of boundary kinematics and global metrics of cardiac function.19. The system of claim 1, wherein to cause display of the image of theheart based on the imaging data, the processor is further configured to:generate at least two images representative of orthogonal cross-sectionsthrough the imaging data; and generate an axis marker on each respectiveimage, indicative of a location where respective planes for the othertwo image cross orthogonally.
 20. The system of claim 9, wherein theprocessor is further configured to: receive a rotate commandcorresponding to an isolated axis; rotate spatial locations by whichintensity values of the inputted data is sampled to align the base andapex of the left ventricle along the axis; and transform the imagingdata corresponding to the image based on the rotations.